CCE Command Line 
 
Using the Command Line Facility
	The Command Line facility provides the capability to automate configuration operations
	which are available in the configuration program.  You can place commands after the
	cce command or in an argument file which the configuration program will use to direct
	its operation.  In addition to checking for commands which follow cce, the configuration
	program always checks for the existance of an argument file named cfgargs.
 
	If no commands are specified after cce or in the cfgargs file, then the configuration 
	program is started normally.  In order to process commands with out starting the
	configuration program's graphical user interface (GUI), an -exit command must exist
	on the program commands, in an argument file, or in the cfgargs file.
 
Syntax of the CCE command
	The correct methods to enter the cce command are:
		Command			How the command works
		cce				Searches for a cfgargs file in the current
						directory (i.e., the directory from which cce
						was invoked).  If the file exists, executes the
						commands in the file.
  
		cce -<command [args ] ...>	Searches for a cfgargs file and processes
						as described above.  Then, processes all
						of the commands specified on the command
						line (following cce).
 
	Please	note, all of the commands, which will described below, start with a minus sign.	
 
Processing of the Command Line
	All commands are processed in the order they are encountered.  The cfgargs file is 
	always processed before commands specified on the command line.  Thus, the command
	line commands have precedence of the cfgargs commands.
 
	A status log, commands.log, is created during command line processing.  Invalid 
	commands encountered are logged.  Problems during command processing are logged.
	As the processing of an individual command completes, a messages is logged containing
	a timestamp, the command name, the value of significant parameters, and whether or
	or not the command was successful.  When all of the command line processing is 
	complete, a final completion message is logged.
 
	Please note, status logging always overwrites the existing commands.log file.
 
Syntax of the Command Line Options	
	Please note, all of the commands begin with a minus sign (-).  Commands and arguments
	are separated from each other by either spaces or tabs.  When commands are specified
	in argument files, the commands and arguments may also be separated by new lines.     
	Parsing of the commands is case insensitive, however, CCE will always display them in
	the format shown below.
 
	-asciiExport <file1 node1 [withComments]... fileN nodeN [withComments]>
		Export the specified node(s) to the specified file(s).  Multiple file/node pairs may
		be specified.  The command line does not validate parameter values.  An
		unmatched parameter at the end of the parameter list will be ignored.  Since 
		comments are not included by default when exporting an ASCII file, the user
		must specify to print comments per desired file.  Muliple -asciiExport commands
		may be specified.
 
	-asciiImport < file1 [withoutLogging] file2 [withoutLogging]... fileN [withoutLogging}>
		Import the specified ascii file(s).  Multiple file names may be specified.  Since
		validation logging is done by default, the user must specify not to log errors per
		desired file.  Multiple -asciiImport commands may be specified.
 
	-binaryExport <file1 node1 file2 node2... fileN nodeN>
		Export the specified node(s) into the specified file(s).  Multiple file/node pairs may
		be specified.  The command line does not validate parameter values.  An 
		unmatched parameter at the end of the parameter list will be ignored.  Multiple
		-asciiExport commands may be specified.
 
	-binaryImport <file1 file2... fileN>
		Import the specified file(s).  Multiple files may be specified.  Multiple -asciiImport
		commands may be specified.
	
	-commandsFrom <commandFile>
		Causes the command line processor to read commands from the specified file.
		The commands will be processed when read.  Thus, commands with in the 
		command file will be inserted into the command line and cfgargs processing.
  
	-deleteNode <node1 node2... nodeN>
		Deletes the specified node(s) from the database.  Multiple nodes may be specified.
		Multiple -deleteNode commands may be specified.
 
	-displayMessages	on/off
		Specifies whether messages should be displayed on the screen.  The default is on.
		When not displaying messags, the default answer, okay, is always returned for all
		message prompts.  If multiple -displayMessages commands are present, the value
		of the last -displayMessages command parsed is used.
 
	-displayStatus	on/off		
		Specifies whether the status log should be displayed on the screen.  The default is
		off.  The user is responsible for closing the status log window.  If multiple
		-displayStatus commands are present, the value of the last -displayStatus command
		parsed is used.
 
	-exit
		Indicates that the GUI should not be started after processing.  Thus, configuration
		operations may be performed in batch mode.
 
	-storeMessages 	on [logFile]
			off	
		Specifies whether messages should be logged to a file.  The default is off.  When
		logging, the default log file is cfg.log.  If multiple -storeMessages commands are
		present, the value of the last -storeMessages command parsed is used.  Please note,
		message logging always appends to the end of existing files.
 
Example Command Line Usage
	cfgargs file contains:	-displayMessages off
				-commandsFrom batch.lst 
				-storeMessages on commands.log
 
	command.lst file contains:	-storeMessages off
					-binaryExport C.zip nodeC
 
	command line:		cce 	-commandsFrom command.lst
					-storeMessages on
					-asciiImport A.acf
					-exit	
	
	batch.lst file conatins:	-storeMessages off
				-asciiImport B.acf withoutLogging
	
	The processing would occur as follows:
		exhaust cfgargs
			set displayMessages off
			-commandsFrom encountered, exhaust batch.lst
				set storeMessages off
				add asciiImport (B.acf withoutLogging) to operations
		continue processing cfgargs (after -commandsFrom option)
			set  storeMessages on with file commands.log
		exhaust command line
			-commandsFrom encounterd, exhaust command.lst
				set storeMessages off
				add binaryExport (C.zip nodeC) to operations
		continue processing command line (after -commandsFrom option)
			set -storeMessages on
			add asciiImport (A.acf) to operations
			do not start GUI after operations are excuted
		execute asciiImport of B.acf withoutLogging
		execute binaryExport of nodeC to C.zip
		execute asciiImport of A.acf
 
	When complete, no messages would have been displayed;  the GUI would
	not be started; and the default log file, cfg.log, would contain four messages 
	(asciiImport for B.acf with timestamp and status, binaryExport for nodeC
	to C.zip with timestamp and status, asciiImport for A.acf with timestamp and
	status, command line processing completetion with timestamp).
		 
			
			
